Description

This PR should address issue with periodic alarms which have exact=true losing accuracy after some time. I believe it is something connected with power optimisations done by different Android versions.
While looking through plugin code I saw that periodic is inconsistent with oneShot calls, since in oneShot users have allowWhileIdle parameter which should call setAndAllowWhileIdle function from AlarmManagerCompat class instead of just set. It means that even with exact set to true periodic alarms were never set to allow while the phone is in idle, which might be the case reported in #487.

It seems that the issue reporter uses Samsung and as an owner of Samsung device as well I know that their implementation of power management is quite aggressive and suspends apps, which aren't used for some days.

Note that this PR is based on #494, because otherwise I couldn't build the example app.

Related Issues

This PR potentially closes #487

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
• All existing and new tests are passing.
• I updated/added relevant documentation (doc comments with ///).
• The analyzer (flutter analyze) does not report any problems on my PR.
• I read and followed the Flutter Style Guide.
• I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

• Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
• No, this is not a breaking change.